Version: $id$
group PICS_ChargingReportResponse_FrontEnd {
// PICS_ChargingReportResponse_FrontEnd parameters.
modulepar {
boolean PIC_reportRecipientId : = true ; boolean PIC_dataReceived : = true ; boolean PIC_versionsResponse : = true ; boolean PIC_obeStatusForDriver : = true ; boolean PIC_accountUpdate : = true ; boolean PIC_responseAuthenticator : = false ;
}
}|
Generated with T3Doc 2.0 on Thu Jan 06 00:06:01 CET 2011.
Description
Does the EUT implement obeId field? Does the EUT implement vehicleLPNr field? Does the EUT implement paymentMeans field? Does the EUT implement serviceProviderContract field? Does the EUT implement tollCharger field? Does the EUT implement timeOfReport field? Does the EUT implement versionInfo field? Does the EUT implement usageStatementList field? Does the EUT implement vatForThisSession field? Does the EUT implement accountStatus field? Does the EUT implement transactionCounter field? Does the EUT implement mileage field? Does the EUT implement listOfCCCAttributes field? Does the EUT implement authenticator field? Electronic fee collection (EFC) — Conformity evaluation of Front End and Back End equipment to ISO 17575-1 — Part 1: Test suite structure and test purpose - Annex B.3: Optinal data elements
Remarks
PICS Reference: Annex B.3.1: ChargeReport